Repository navigation
chore(release): 5.1.0 notes for PRs merged during review - #2033
Open
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
Open
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
Conversation
Mikola Lysenko (mikolalysenko)
enabled auto-merge
November 6, 2026 21:06
Mikola Lysenko (mikolalysenko)
added
the
Ready for review
Collaborator
Author
|
Labeled Ready for review by the burn-down agent.
Generated by Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #2032: notes for four PRs that landed while it was in review
#2032 covered
v5.0.1..7bde3ba. Before it merged, four more PRs landed onmain(c6a4fda6..502aa1fc). They ship in 5.1.0 because the Release workflow hasn't been dispatched yet, so they need entries in the[5.1.0]section first.This PR changes only
CHANGELOG.md(+12/−1, inside## [5.1.0]). The version stays 5.1.0, and the new entries don't change the version bump.redirect_vlt_artifact_unverifiableis no longer raised, and the in-memory engine (Node addon,hosted-bundle) pins vlt deps instead of withholding them as offlinesource … doblocks is attributed to the innermost block, so hosted rollback/remove on Bundler ≤ 2.1 no longer refuses withhosted_wiring_contestedDouble-check: #2013 could arguably go under
### Changed, since it drops the encoding check rather than fixing a bug. The version is minor either way.Local checks:
release-lint.sh --stable-only --tag-checkpassed, andrelease.py changelog check --version 5.1.0passed.Maintainer checklist
git log --first-parent <this PR's merge SHA>..origin/main.main(optionally adry-run: truerun first).@socketsecurity/socket-patchlast.Generated by a one-off release-staging routine.
Generated by Claude Code
Note
Low Risk
Changelog-only; no runtime or release automation logic changed in this diff.
Overview
Documents four follow-up fixes in the
[5.1.0]section so they ship with the next release cut.Fixed → RubyGems. Records that gems inside nested
source … doblocks are credited to the innermost block like Bundler, so hostedrollback/removeno longer hithosted_wiring_contestedon Bundler 2.1 and older (#1997, #1999).Fixed → npm family. Records hosted vlt behavior: scans stop downloading every granted patch archive for encoding checks and no longer emit
redirect_vlt_artifact_unverifiable; re-encoded mirrors failvlt ciwithEINTEGRITY; the in-memory hosted path (Node addon,hosted-bundle) pins vlt dependencies instead of treating them as offline-only (#2013).Maintenance. Extends the test/CI bullet with #2000 and notes that release workflow artifact steps no longer use Node 20 actions (#2027).
Reviewed by Cursor Bugbot for commit 5d76313. Configure here.
Generated by Claude Code